Distributed web/SFSB expiration after failover schedules premature expiration

Distributed web/SFSB expiration schedules expiration the corresponding session/bean is closed. When the request handling the session/bean is not the primary owner, the expiration is scheduled on the primary owner. However, because the command is dispatched synchronously, if the backing cache is transactional, the primary owner will schedule expiration for the previous last accessed time, instead of the current last accessed time.