Although it was expected(/known) that the "Class-Path" entries in MANIFEST.MF cause EJB3 deployments to malfunction, an empty Class-Path element wasn't expected to cause anything like this. Could you please file a JIRA here https://jira.jboss.org/jira/browse/EJBTHREE so we can track and fix it accordingly. Please (if possible) attach any logs or sample application which demonstrates this issue. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4244709#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...