Threadlocal is great! It can help you get out of sticky situations, and give you a great boost of performance and/or isolation. But with great tools comes great responsibility. Threadlocal can also be misused, and create memory leaks, or object corruption, and unknown sharing. So if you ever had seen one and never quite got what it does, or even if you were consider using one. Take a listen! And steer the people in the right way for the use of Threadlocal.
Also, Thanks Michael for pointing the issue with episode 55 and rebasing! Don't forget to SUBSCRIBE to our cool new NewsCast!
Java Off Heap

https://docs.oracle.com/javase/7/docs/api/java/lang/ThreadLocal.html
http://tutorials.jenkov.com/java-concurrency/threadlocal.html
http://jsr166-concurrency.10961.n7.nabble.com/Threadlocals-and-memory-leaks-in-J2EE-td3960.html

Do you like the episodes? Want more? Help us out! Buy us a beer!