Ah HA!
I've seen this behavior, but I just worked around it. I get jsessionid's appearing early on in the conversation, but eventually things settle down and they go away. The caused quite the bedlam when my security code didn't take in to account the jsessionid being on the URL.
I've since worked around it, but it will be nice when this gets rolled in to the release.
[Message sent by forum member 'whartung' (whartung)]
http://forums.java.net/jive/thread.jspa?messageID=252360