The concept of a conversation will be familiar to those of us that have developed applications with Seam 2. In CDI, the conversation scope is very similar to the session scope, with the main difference being that its activation and deactivation is controlled by our application and not the container.
The conversation scope is also associated with a particular browser tab of a user, unlike the session, which is typically shared between tabs by browsers.
Each conversation is a way to represent a single unit of work that a user will perform to achieve a specific goal or task. As the conversation context holds the state associated with a unit of work by the user, there will be multiple conversations for a single user if they are working on multiple tasks at the same time.