Improved OOME handling. 

Enhanced default OOME handler to be able to distinguish a real lack of memory from a failing large allocation. Injected some missing OOME dispatching points in internal Hazelcast threads.
You are right with the responsibility. 

What would you suggest as a good solution to prevent swallowing the OOME? I think swallowing it is just wrong. OOME can happen at any time (during allocation?) and if we just swallow it then it might be extremely hard/unpredictable/seemingly_magic when troubleshooting.