In this case the problem is that the drawable instance is stored statically in a class (so it will never get garbage collected) and it keeps a reference to an activity, which means the activity won't be garbage collected as well (even if it's terminated). Hence the memory leak.
In your debugger you could inspect the drawable instance and see if there is any field that references another view/context.
But just avoid storing UI stuff statically and it will solve a lot of issues like that :)