fix: clean up rate limiter on WebSocket disconnect (memory leak)

WebSocket close handler was missing getRateLimiter().removeClient(clientId),
causing rate limiter entries to accumulate per-client and never get freed.
TCP already did this correctly; now WebSocket matches.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: egeominotti

docs/src/content/docs/changelog.md

@@ -10,6 +10,11 @@ head:
 
 All notable changes to bunqueue are documented here.
 
+## [2.6.101] - 2026-04-02
+
+### Fixed
+- **WebSocket rate limiter leak** — WebSocket disconnect handler was not calling `removeClient()` on the rate limiter, causing per-client rate limiter state to accumulate indefinitely. TCP already did this correctly; now WebSocket matches.
+
 ## [2.6.100] - 2026-04-02
 
 ### Fixed

package.json

@@ -1,6 +1,6 @@
 {
   "name": "bunqueue",
-  "version": "2.6.100",
+  "version": "2.6.101",
   "description": "High-performance job queue for Bun & AI agents. SQLite persistence, cron scheduling, priorities, retries, DLQ, webhooks, native MCP server. Zero external dependencies.",
   "type": "module",
   "main": "dist/main.js",

src/infrastructure/server/http.ts

@@ -215,6 +215,7 @@ export function createHttpServer(queueManager: QueueManager, config: HttpServerC
     close(ws: ServerWebSocket<WsData>) {
       const clientId = ws.data.id;
       wsHandler.onClose(ws);
+      getRateLimiter().removeClient(clientId);
       queueManager.unregisterWorkersByClientId(clientId);
       queueManager
         .releaseClientJobs(clientId)