I am using jboss-3.2.1_tomcat-4.1.24 and I just encountered a very strange ClassLoader problem. I have 3 pieces of code: Utility classes, EJB's, and a Web-app. They are all inside 1 ear file. During initial development everything was fine. I put my utility jar file inside the /webi-inf/lib directory and the webapp found it without a problem. Today, I did more work on my EJB's. I used a class from my utilites jar and, as expected, I got an error during deployment saying the class could not be found. To fix that I added a Class-Path: library/org.moss.utilities.jar entry into the MANIFEST file of the EJB jar. I was able to deploy the EJB without a problem. However, Adding that line to the manifest screwed up deployment of the WAR. Now my WAR file is getting ClassNotFound exceptions when the filters and servelt try to start. If I remove the manfest entry for the bean, the WAR deploys fine just as it did before.