AFAICS, if an EJB2 session bean is defined in the ejb-jar.xml version 3 then the EJB3 deployer creates the EJB3 container with the EJB2 client view for the bean. Is this really how it is supposed to work? Looking at the test I suspect the setSessionContext(...) is not called on the instance when it is created. Even though I see the Resource annotation is added for the method in the Ejb3DescriptorHandler. Or maybe it doesn't get there or the injection is not performed... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4145570#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...