Hardening/false leaks

### Description
Fixed the new SIGSEGV  - moved the call to mongDisconnect to a higher level.
Fixed the two leaks (197 bytes each) - deleting triggeredSubscriptions filtered by throttling.

So at then end we are keeping pthread_setcancelstate() without knowing if this may introduce blocking issues? :) Or maybe the plan is to have them in this PR to study the behaviour of the CB once it get merged into develop?