I can't reproduce the memory leak. valgrind's output doesn't show suspicious memory leaks.

./configure --with-pydebug --config-cache
valgrind --suppressions=Misc/valgrind-python.supp ./python Lib/test/test_ssl.py

Python 3.4 tip
--------------

==26085== HEAP SUMMARY:
==26085==     in use at exit: 1,286,703 bytes in 3,778 blocks
==26085==   total heap usage: 210,241 allocs, 206,463 frees, 62,923,839 bytes allocated
==26085== 
==26085== LEAK SUMMARY:
==26085==    definitely lost: 0 bytes in 0 blocks
==26085==    indirectly lost: 0 bytes in 0 blocks
==26085==      possibly lost: 1,148,038 bytes in 555 blocks
==26085==    still reachable: 138,665 bytes in 3,223 blocks
==26085==         suppressed: 0 bytes in 0 blocks


Python 3.4.0a1 (without patch)
------------------------------
==32513== HEAP SUMMARY:
==32513==     in use at exit: 1,708,298 bytes in 4,120 blocks
==32513==   total heap usage: 237,965 allocs, 233,845 frees, 94,637,130 bytes allocated
==32513== 
==32513== LEAK SUMMARY:
==32513==    definitely lost: 0 bytes in 0 blocks
==32513==    indirectly lost: 0 bytes in 0 blocks
==32513==      possibly lost: 1,568,077 bytes in 893 blocks
==32513==    still reachable: 140,221 bytes in 3,227 blocks
==32513==         suppressed: 0 bytes in 0 blocks
==32513== Rerun with --leak-check=full to see details of leaked memory


Python 2.7 tip
--------------

==3184== HEAP SUMMARY:
==3184==     in use at exit: 6,411,895 bytes in 4,757 blocks
==3184==   total heap usage: 16,245 allocs, 11,488 frees, 32,948,412 bytes allocated
==3184== 
==3184== LEAK SUMMARY:
==3184==    definitely lost: 0 bytes in 0 blocks
==3184==    indirectly lost: 0 bytes in 0 blocks
==3184==      possibly lost: 1,823,596 bytes in 1,505 blocks
==3184==    still reachable: 4,588,299 bytes in 3,252 blocks
==3184==         suppressed: 0 bytes in 0 blocks