VConnection is a vClient object - it does not matter for vServer. vServer counts connections in different way.

vServer destroys "connection" when:
- vClient does not pass login procedure (wrong credential...);
- vClient performs connection.Close;
- vClient suddenly disconnected (socket closed);
- connection timeout reached;

"dead" vClient connection is not connected to vServer anymore - you just can do nothing with it.
In some cases (different for Mac, Linux and Win) the "suddenly disconnected" vClients might be detected with some lag (usually few seconds but it could be minutes).

This doesn't seem to be what it's happening to me. It seems that the dead vClient connection is still in the VServer memory forever (or, if you say "some lag (usually few seconds but it could be minutes)", I would say perhaps some *days*).
This situation lead me to forbid a user to connect to the server if there are already 5 connections (as I have a 5 connections license) even if all of these connections (or some) are dead. And this force me to restart the server as I cannot connect anymore to the VServer from a VClient to cancel the dead connections.

And I haven't see any INI parameter to change this behavior. Or perhaps have I misunderstood the "MaxIdleClientTimeout" parameter that is set to 0 here. I don't think it is as the value of this parameter is in minutes and I need a way to reconnect in a few seconds.

Please, send me a vServer log (VerboseMode = 3)

Done.
You will see that after the 5th broken (dead/not closed properly) connection, I cannot connect anymore as the server has kept in memory the 5 connections and thus (in my case) the connections limit is reached.
I would like to not be forced to restart the server in this case !