You need to explicitly set the conversation id yourself - something like this should work:
But how can my client/view get the ID of the current long-running conversation (not nested) running on the server? Before I make any remote method call, the consersation ID returned by Seam.Remoting.getContext().getConversationId() is null.
Thanks for the response!
Shane, thanks for your help. Got me down the right path, then I discovered how to get the current conversation ID from my view, which was the last missing link.
In case it saves someone else some grief, here is how I got the current conversation ID:
I've updated the documentation to describe this now.