McKenzie,
I agree with you. HttpSession having the session info and using a stateless bean would theoretically have better scalability, but as the container's capability to passivate and then reload the state thru activate is becoming more competent, I think SFSB may be a better solution. Ofcourse, the need to passivate and activate may seem to be overhead here, but we need to look at the memory requirements also.
If our app is doing good in the given(tuned) JVM params, it isokay, if not, we keep the HttpSession light... Is this a right argument???