Conversations creates session in Java application too early

Creating a session on the first visit to a website is considered bad form as it can adversely affect performance.

Conversations has a decorator called: RequestHandlerDecorator
As the decorator is called for every request it will be called on first visit to a site.

Down in the call stack of the decorator is ConversationManagerImpl.getConversations
This method calls request.getSession(true) which forces a session to be created.
This needs to be reworked so that getSession(true) is only called once the first conversation has been started.
You should be able to call getSession(false) to detect whether a session has been called or not yet.

One consequence of the session being created is that a jsessionid attribute is set in the URL sent to Facebook for federated login.