Memory leak in WebSocket connection handler

The WebSocket handler doesn't properly clean up connections when clients disconnect unexpectedly. This causes memory usage to grow over time in production.

**Steps to reproduce:**

1. Open 100+ concurrent WebSocket connections

2. Force-close browser tabs

3. Monitor server memory

**Expected:** Memory returns to baseline

**Actual:** Memory keeps growing