Testcase decription:
1. Process A creates channel via ChannelCreate() function and waiting for incoming data requests.
2. Process B create incoming data channel via ChannelCreate() and connects to Process A
   (ConnectAttach() to procA channel) and send handshake message via this channel and pass incoming data channel id.
3. Process A pick up this message via MsgRead(), then ConnectAttach() to procB channel and 
   create additional channel via ChannelCreate() function and pass this channel id to procB via MsgReplyv.
4. Process B got reply and call ConnectAttach() to newly created channel. 
   So basicly we have one requests processing channel and then for every new connection we create read 
   and write channels. It was done to support tcp like server connection handling.

5. Then process B send data message to process A.
6. Process A pick up this message and send it back (like ping).
7. Process B got message from process A and disconnects from process A via ConnectDettach() 
   and destroy it own channel via ChannelDestroy().
8. Process A do the same thing as proc B #7 but for it's own part of connection.
   Both ConnectDettach() and ChannelDestroy() succeded.
9. After that process B go to step #2 and repeat all the steps again and again until it got some error.


And actually this scenario works fine but we found that every time we create new channel at process A
it has new incremented id. And at some point we were faced with problem that process A coudnt create 
more Channels(ChannelCreate). And we understand that we have somekind of resource leak here but as far 
as we understand we are doing everything to cleanup resources. Maybe you can reveal some light 
in this case. 
Also we found that if we eventually close accepting channel (process A)- all outstanding channels ids became free 
and we cound start over.

Script test.sh shows up this problem.

One more thing, when you start process A and process B in the same terminal you could see 
resource leak after a while(the way like test.sh do this). But when you start them in different 
terminal you'll see warning messages on second iteration.

