Memory lick in the SSL-API?

If I’m not mistaken, there’s a memory lick in the SSL-API (NET+OS 6.0)! After each SSL-connection there are 208 bytes less in the heap! Following situation (sample code): 1) client_socket = socket(AF_INET, SOCK_STREAM, 0); 2) connect(client_socket, &serverAddr, sizeof( serverAddr)); 3) secure_socket = NASSLConnect(client_socket, cipher_list, cipher_list_len); 4) closesocket(secure_socket); The functions return successfully, but after any cycle (create socket, connect, SSL-connect, closesocket) the available memory space is reduced at 208 bytes. I hope that someone could give helpful advises to fix this problem. thx mike