I published a detailed step by step guide, including real life samples, for using the FB4 new object references view to quickly track down the root of a memory leak, straight down to the exact line of code causing it. it's here: http://www.tikalk.com/flex/solving-memory-leaks-using-flash-builder-4-profiler
