Stale listener UUIDs cause Redis publish amplification after reconnects

Each reconnect creates a new listener UUID and adds it to the producer’s listenerChannels array. When a consumer disconnects, it only unsubscribes from its Redis chunk channel; the producer is never told to remove that listener ID.

As a result, every future chunk is published to every listener ever registered during that stream, including disconnected listeners.

Example: if a user disconnects and reconnects five times, the producer may issue five PUBLISH commands per chunk even though only the latest listener is active. For 500 remaining chunks, that becomes 2,500 publishes instead of 500.

The producer should remove inactive listener IDs while preserving support for multiple genuinely active consumers.

Trace the reconnect and disconnect handling around the producer’s listenerChannels array and Redis chunk-channel subscriptions. Reproduce the reconnect scenario described in the issue, then verify that inactive listener IDs are removed while multiple active consumers still receive each chunk without duplicate publishes.