Live Preview concurrent WebSocket session limit configuration

Goal: Determine whether Stackblitz imposes a limit on the number of simultaneous Live Preview WebSocket connections that can be opened for a single project, and whether this limit can be adjusted.

Constraints: The Live Preview documentation states that a session is created per browser tab but does not specify a hard maximum or provide a user‑configurable setting for concurrent sessions. Idle WebSocket connection timeout is also undocumented, raising uncertainty about how long stale connections occupy backend resources.

Uncertainty: Without explicit limits or timeout values, opening many tabs with Live Preview may lead to delayed updates or disconnections, suggesting possible backend connection‑pool pressure.

Questions: What is the maximum number of concurrent Live Preview WebSocket connections allowed per project? Does Stackblitz enforce an idle timeout for Live Preview WebSocket connections, and if so, what is the duration? Can users request or configure a higher limit for Live Preview sessions?