I will answer this question here, but for those reading the response, if you want to see book-specific questions answered, you should post them on the Seam in Action forums (or else I might never see the question).
Moving on, the default scope of a SFSB is conversation. Conversations are stored in the HTTP Session, but in an isolated region that is managed as a conversation. Don't confuse the word
sessionin SFSB with HTTP session. They are different things. The
sessionin SFSB just means that it is not terminated until removed by the client that is holding on to it. Putting it in the long-running conversation allows it to survive over a period of requests. In the old days, it was stored in the HTTP session, but now the preferred way is to use the conversation.