Anycable websocket connections not closed

Hello again.

we are using kong to balance our websocket connections to 3 anycable-go in production.
Since we use kong we have the problem that our websocket connections are not properly closed anymore. Usually we had a maximum around 800 concurrent connections per day. When we used the default nginx kubernetes load balancer the open connections reduced during the night.

Since we setup kong the connections sum up until 8k connections and kong gets restarted by kubernetes because it can’t handle connections any more.
image

I also asked this question to the guys from anycable-go here:

What could be the reason for this problem?
Any settings I could try?

Thanks for your help.