class-path in MANIFEST.MF should still work when you specify it for your ejb jar, war file, or even library jars. But it can be tricky to specify the path. It could be that your class-path has always been ignored, but in previous version, the sever included all top-level jars in classpath.
Now that we have the ear/lib mechanism, it should be the preferred way.
[Message sent by forum member 'cf126330']
http://forums.java.net/jive/thread.jspa?messageID=476814