It should work but you are probably encountering a problem with specifying the full class name, including the package in your ejb-jar.xml. JBoss 2.x didn't worry too much about this but you may find that this has been tightened somewhat and more compliant with the spec.
Unless your classes don't specify a package. So just check your deployment descriptors. Most likely that is the issue.
Hope it helps as I'm guessing. If it is not, post your deployment descriptors and I'm sure someone will have an answer.
thanks for your reply.
The actual problem is my startup class was accessing the beans before they got deployed. I need to make jboss invoke the startup class after all ejb's get deployed.
A surprising error message - did you solve the problem?