I have never used @SerializedConcurrentAccess, but I'm sure it is not the exactly the same. (practically speaking, it may be roughly equivalent though - but I haven't looked into it) You are actually right, seam does serialize access to stateful session beans. I didn't realize we did that. I went ahead and tried the test and the only way I could get anything to happen was by adding a Thread.sleep() to the delete action. And then, I got the expected result: The conversation ended, timed out or was processing another request I wonder what is happening in your case to make it not work... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3998299#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...