After a lot of discussion, we've decided to revert this fix. It's not reasonable to assume that one single config value could optimize all possible Session sizes within an app, even within a benchmark. Instead, we'll be following up with a new "Session template" concept that would let users create named templates that override the default Session options, including the addition of a "how many entities will this session manage".