test_ready_remove_worker broken on Python 3.11

[hendrikmakait]

It looks #7698 broke test_ready_remove_worker on Python 3.11:

This test fails with RuntimeError: ('Unclosed Comms', [<TCP (closed) ConnectionPool local=tcp://127.0.0.1:62390 remote=tcp://127.0.0.1:62381>, <TCP (closed) ConnectionPool local=tcp://127.0.0.1:62391 remote=tcp://127.0.0.1:62381>]).
(https://github.com/dask/distributed/actions/runs/5690294964/job/15423369445#step:19:1681)

cc @graingert

[crusaderky]

Ah you beat me two it.
There are two more tests that started failing at the same time, test_closed_worker_during_shuffle and test_restarting_during_transfer_raises_killed_worker.
XREF #8055

[crusaderky]

Timing and topic point to #7698. If a resolution is not trivial, maybe we should revert it for the time being?

[hendrikmakait]

Regarding the P2P errors, I've described the problem over here: #8011

[hendrikmakait]

I'll dig deeper into test_ready_remove_worker but if it's hard to fix, I agree that we should revert #7698 and solve its issues before merging it back into main. cc @fjetter

[fjetter]

I don't want to revert #7698 just because of a couple of leaked connections. This PR has a significant real world impact and I'd rather temporarily disable the connection leak detection that reverting this PR

[hendrikmakait]

I don't want to revert #7698 just because of a couple of leaked connections. This PR has a significant real world impact and I'd rather temporarily disable the connection leak detection that reverting this PR

Works for me, after an initial investigation the leak doesn't seem to be trivial to fix.