Licensing works as such: the maximum number of concurrent client connections is defined in the license. Only active websocket connections count against the limits, so there is no "correct logout" required for the license to be freed as will be automatically freed once the websocket connection is closed, regardless of whether this was cleanly or through an error.
However, as the WiFi connection breaks (which is the error), the ctrlX OS cannot detect immediately that the websocket connection has been broken (this is how TCP networking works, this has nothing to do with WebIQ itself) and keeps that connection as open towards WebIQ Server on your ctrlX until a timeout occurs. That is when WebIQ Server will be notified by the OS that the connection has been closed and the license will be freed. This can take between 30 seconds and 2 minutes depending on the timeout setting on the system and has nothing to do with the robot reboot.
As that timeout is an OS setting and should be the same for all network connections on the ctrlX that probably would have to be changed on that level as a workaround.
However, as the reason for the error is the WiFi connectivity to prevent the issue a better WiFi connection is recommended as the timeout change would only be a workaround.
