Right now, the notion of how beans are stored are ambiguous. The implementations back them by maps. This may work well, but there's some amount of plugability required to make passivation capable beans work right. A single request makes sense to store in a map. Sessions are stored in the HTTPSession. We should allow these bean stores to be more pluggable, allowing users or implementations to override how their beans are stored.