At this point, this looks like a bean deployment problem rather than a classloader issue. The JNDI tree output suggests that the bean proxies are bound correctly. So let's remove the WAR file from the picture and just try deploying the EAR file containing the EJB jar. Try this: - Remove the WAR file from the deploy folder - Copy the EAR (containing the ejb jar) to the deploy folder - Start JBoss - Post the deployment logs from the server.log file. Please ensure that you post the logs only from the point when your application deployment starts. The server.log is too verbose and posting the entire logs here wont be useful :-) - Also please access the JNDI tree again after the deployment is done and post the output here again. Just want to see how the JNDI contents for this bean look like when the WAR is not in picture. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4190869#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...