There are a couple of things tied together: - getInvokedBusinessInterface returns an interface based on method signature - multiple local business interfaces doesn't work properly - EJB 3 4.7.1: generated classes - EJBTHREE-786: remove method If we take 4.7.1 literaly then we must have a proxy class for each interface that the bean has. I don't know if TCK demands such a thing. But if we want to know for sure which interface was invoked we need to have different proxies and thus different bindings. This would also resolve EJBTHREE-786. Note that in a lot of code the distinction between a local business interface and a local 2.1 interface isn't properly made. The question is does it eliminate the possiblity for a combined binding (issue 540)? Probably not, but it would make things more complicated. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4090344#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...