"jaikiran" wrote : I think i got an answer to this question. The SessionContainer infact is part of the proxy. So the testcase too can go there. I don't know why, so far, i have been thinking that the problem was in the ejb3-test module :) (probably the package org.jboss.ejb3.test confused me). Looks like it. That SessionContainer is a mock container which is part of EJB3 Proxy (as Proxy knows nothing about the *real* containers in EJB3 Core). So SessionContainer there just implements InvokableContext.invoke(), and has its own handling. Go ahead and create an issue, commit the testcase for it, and try for a fix on the SessionContainer in proxy tests. S, ALR View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4169196#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...