This bug is probably more noticeable if you're using the memcache session handler rather than the default (filesystem) session handler. I think the memcache session handler uses session.gc_maxlifetime as the hard expiration date for sessions; whereas in the default filesystem session handler they may stick around until the garbage handler runs.
This bug is probably more noticeable if you're using the memcache session handler rather than the default (filesystem) session handler. I think the memcache session handler uses session. gc_maxlifetime as the hard expiration date for sessions; whereas in the default filesystem session handler they may stick around until the garbage handler runs.