With the implementation of EJBTHREE-768 we've a clash on the usage of EJBObject. We had functionality that allowed each proxy to be an EJBObject. So now this test is failing: org.jboss.ejb3.test.stateful.unit.RemoteUnitTestCase.testEJBObject For terminology purposes I quote the spec: "EJB 3 3.1" wrote : Terminology note: This speci?cation uses the term remote business interface to refer to the business interface of an EJB 3.0 session bean that supports remote access. The term remote interface is used to refer to the remote component interface of the EJB 2.1 client view. The term local business interface refers to the local business interface of an EJB 3.0 session bean that supports local access. The term local interface is used to refer to the local component interface of the EJB 2.1 client view. It is important to note that 'remote interface != remote business interface'. I say what we had is a spec violation (you know me :-)). "EJB 3 4.3.3" wrote : The getEJBObject method returns the session bean?s remote interface. Only session beans with a remote EJBObject interface can call this method. "EJB 3 4.6.6" wrote : The [session bean's business] interface must not extend the javax.ejb.EJBObject or javax.ejb.EJBLocalObject interface. "EJB 3 4.6.7" wrote : The [session bean's remote] interface must extend the javax.ejb.EJBObject interface. Which leads to the question: for what scenario did we have this functionality? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4091948#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...