I see the same behaviour in 3.0.0, but it is fixed in the 3.0.1 download! So run and get it :-)
Btw, the problem is that the jasper jsp compeler does not get the right classpath when it is run, so other uses of the classes from the jar works in 3.0.0.
My structure is:
The ejb is deployed as a ejb module and myweb as a webmodule by application.xml.
The only classpath i need in the manifest.mf is that I have
in the manifests for myweb.war and myejb.jar.
You do not need to have a a classpath entry to get the classes in the ejb if it is deployed.
Ok, thanx for the help! I'll try out 3.0.1 at once. Strangely I could only find the download on the download-page at sourceforge, not here att jboss.