I'm seeing the same 3 errors in the appclient tck tests as currently seen in the tck runs: http://hudson.qa.jboss.com/hudson/view/TCK5/job/tck5-appclient/lastBuild/... in the mc/vfs appclient work I'm doing, so its just a general regression in the jndi name of the ejb remote home. The home is resolving to the descriptor jndi-name, but the home is bound under ear-name/bean-name/home. These tests are effectively deploying ejb2.x beans as ejb3.x beans(no annotations, just a v3 ejb-jar.xml), and a j2ee 1.4 or earlier client is linking to the ejb using its bean name. Its a descriptor ejb-ref with a remote/home specified. The issue is that the MappedReferenceMetaDataResolverDeployer will have to resolve the ejb-ref differently based on whether the target ejb is a 2.x or 3.x. We should have this info available in the binding policy, so I need to see what is going on with not using it. I guess its just that the server specified binding policy is not in synch with the current ejb3 behavior. Is the ejb3 proxy layer using the deployment binding policy for all proxies yet? Looking at the code this does not appear to be the case. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4165971#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...