Earlier quoted context omitted.
Are you saying that the memory allocated by the memoizer is not recoverable e.g. won't be released until the browser is killed? If not then it is not a memory leak.
It's potentially recoverable, but stuck in some "private" object your JavaScript application will never bother to look at. It's still a memory leak.
[deleted]