The performance of many enterprise Java applications can typically be poor, forcing affected companies to pay the high price of lost sales and tarnished reputations. Fortunately, proactive attention to the performance of an application while it is being developed can eliminate most performance issues before your customers ever see them. This paper presents a strategy for identifying memory leaks in Java applications from the comfort of the Eclipse Java Integrated Development Environment (IDE). You will learn how the Java garbage collector works, the nature of memory leaks, and how to avoid them. You will also learn how to configure the automated analysis of unit test case memory usage inside Eclipse, while learning strategies for isolating and resolving memory leaks. Lastly, I will explain how to regularly generate memory profiles in a repeatable fashion. Because everything runs from inside Eclipse, you can generate memory profiles and summary reports with the click of a mouse once Eclipse is configured.