1) I don't think so 2) W currently add the tx id to the client side invocation if there's an active tx. I don't think adding a tx context to the remoting marshalling would have any impact on us - you would just be adding tx context to the response? What would client side remoting do with the response context? 3) The only explicit marshalling ejb3 does is for calls to a @Remote interface so the call is call-by value per the spec. We use org.jboss.serial.io.MarshalledObjectForLocalCalls(invocation). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4135148#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...