I don't know why you just spent so many words on explaining me the current behavior. I know what the current behavior is. I know how it behaved in the test case you submitted. I'm happy with it. There is a massive difference between what happens when you call @Begin(id="...") when there is no long-running conversation in progress, and what happens when there is already one in progress. The stuff written in the documentation refers to the case where there is no conversation in progress. Nevertheless, both cases are at least somewhat broken because they result in changing the conversation context in the middle of a request. You should use the new functionality for defining "natural" conversation ids, since it is not vulnerable to this problem. Yes, I understand that this is not yet documented, but its pretty easy to figure out. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032260#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...