Exceeded maximum number of I/O connections: Further forward open requests not properly rejected

When opening an unlimited number of class 3 connections, for the first connections the device answers nicely, but when the maximum number of connections (64) is exhausted, then the requests are not correctly answered with an error code, but are still answered with the success error code in a (according to wireshark) malformed packet.

Furthermore, doing this has bad effects, as the ARM sometimes ends up in its exception vectors afterwards.