Websocket Issue V16

Since yesterday (I think), I am expiriencing issues syncing.
On the Kodi-side:
* Log in works, it starts to try to sync, eventually a error message apperas.

On the jellyfin side:
* A lot of web-socket connections are and remain open, eventually the CPU usage is 100% (~40 jellyfin processes, cause 16 CPU-Cores to have 100% usage).

Example logs:
> ...
[2026-09-11 13:52:57.517 +00:00] [INF] [32] Jellyfin.Plugin.KodiSyncQueue.API.KodiSyncQueueController: Plugin Settings Requested...
[2026-09-11 13:52:58.418 +00:00] [INF] [33] Jellyfin.Plugin.KodiSyncQueue.API.KodiSyncQueueController: Sync Requested for UserID: '06c92835-9dd8-47a6-a9be-f1ee00c0a1c1' with LastUpdateDT: '"2026-09-09T19:40:26Z"'
[2026-09-11 13:53:28.437 +00:00] [INF] [35] Jellyfin.Plugin.KodiSyncQueue.API.KodiSyncQueueController: Sync Requested for UserID: '00000000-0000-0000-0000-000000000000' with LastUpdateDT: '"2026-09-09T19:40:26Z"'
[2026-09-11 13:53:58.490 +00:00] [INF] [32] Jellyfin.Plugin.KodiSyncQueue.API.KodiSyncQueueController: Sync Requested for UserID: '00000000-0000-0000-0000-000000000000' with LastUpdateDT: '"2026-09-09T19:40:26Z"'
[2026-09-11 13:54:02.027 +00:00] [INF] [27] Emby.Server.Implementations.Session.SessionWebSocketListener: Lost 1 WebSockets.
[2026-09-11 13:54:10.008 +00:00] [WRN] [27] Emby.Server.Implementations.HttpServer.WebSocketConnection: WS "192.168.1.252" error receiving data: "The remote party closed the WebSocket connection without completing the close handshake."
[2026-09-11 13:54:10.010 +00:00] [INF] [27] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "192.168.1.252" closed
[2026-09-11 13:54:20.283 +00:00] [INF] [36] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "192.168.1.252" request
[2026-09-11 13:54:28.530 +00:00] [INF] [7] Jellyfin.Plugin.KodiSyncQueue.API.KodiSyncQueueController: Sync Requested for UserID: '00000000-0000-0000-0000-000000000000' with LastUpdateDT: '"2026-09-09T19:40:26Z"'
[2026-09-11 13:54:59.538 +00:00] [INF] [36] Jellyfin.Plugin.KodiSyncQueue.API.KodiSyncQueueController: Sync Requested for UserID: '00000000-0000-0000-0000-000000000000' with LastUpdateDT: '"2026-09-09T19:40:26Z"'
[2026-09-11 13:55:24.742 +00:00] [INF] [34] Emby.Server.Implementations.Session.SessionWebSocketListener: Lost 1 WebSockets.
[2026-09-11 13:55:29.632 +00:00] [INF] [34] Jellyfin.Plugin.KodiSyncQueue.API.KodiSyncQueueController: Sync Requested for UserID: '00000000-0000-0000-0000-000000000000' with LastUpdateDT: '"2026-09-09T19:40:26Z"'
[2026-09-11 13:55:30.299 +00:00] [WRN] [38] Emby.Server.Implementations.HttpServer.WebSocketConnection: WS "192.168.1.252" error receiving data: "The remote party closed the WebSocket connection without completing the close handshake."
[2026-09-11 13:55:30.301 +00:00] [INF] [38] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "192.168.1.252" closed
[2026-09-11 13:55:40.427 +00:00] [INF] [38] Emby.Server.Implementations.HttpServer.WebSocketManager: WS "192.168.1.252" request
[2026-09-11 13:55:59.647 +00:00] [INF] [38] Jellyfin.Plugin.KodiSyncQueue.API.KodiSyncQueueController: Sync Requested for UserID: '00000000-0000-0000-0000-000000000000' with LastUpdateDT: '"2026-09-09T19:40:26Z"'

Start by reproducing the Kodi sync failure and reviewing the logged requests in Jellyfin.Plugin.KodiSyncQueue.API.KodiSyncQueueController alongside the WebSocketConnection and WebSocketManager messages. Trace why repeated sync requests and reconnects leave WebSockets open. Done means Kodi sync completes, connections close cleanly, and CPU usage does not remain saturated.

Written by the indexing model from the issue text.