Excessive use of sessions can cause a pool to stop?
Assuming it is a memory overflow, in this case, it results in exceptions also accounted for in the pool failure protection settings or in immediate stop, or recycling?
Is there an IIS log that indicates the effective stopping of the pool for any reason? Overflow of memory, exceptions in excess configuration, etc?