I often run EurekaLog as well as MadExcept when debugging and I have not seen any memory leaks reported either for TImageEnMView in recent 5x versions by either.
But... do you get leaks if you remove ImageEnMView1.Proc.UndoLimit := 5?
I will investigate, though I doubt it is a memory leak. There are a number of objects that are created once and left for clean-up on app closure (to delay their destruction).