Many connections closed simultaneously

[DavidFeliot]

When using hawtdispatch-transport, the call to 'Selector.selectNow' done in the method 'cancel' of NioManager is very costly if many connections are closed simultaneously while some other connections are still open (and working). The closing connections consume all the CPU time (because of 'selectNow') preventing the open connections from working. Would it be possible to add an option that would disable the call to 'selectNow' done in 'cancel'? In that case 'selectNow' would be called later in 'NioManager.select'.