Interesting responses. anonymous wrote : That's a pretty rubbish workaround. The only one I've come up with that doesn't involve lots of changes to existing code is to not use JBoss 5. It's very disappointing. GColeman, I only had to remove two @EJB annotations because the application I'm working on is mostly ejb2. The only other option appeared to be reworking how everything is packaged which in my case would have taken significantly longer than the few minutes it took to remove the annotations. anonymous wrote : Couldn't agree more. Wolfc, I assume you agree with the rubbish comment and not with GColeman's comment about how disappointing JBoss 5 is. anonymous wrote : So making sure the actual EJBs are not in a jar which is in lib (optionally specifying it as an ejb module in application.xml) should resolve the problem. Rubbish! ;-) Your suggestion will take significantly longer than removing two @EJB annotations. I'm not arguing that removing the @EJB is a good solution but in my case it is a very simple way of getting my application deployed on JBoss 5. It appears that this isn't an option for GColeman. What I really want is for JBoss 5 to be able to handle @EJB annotations correctly without any workarounds. Jeff Brooks View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4178641#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...