I said "perhaps" because while it might be misleading in the sense that this isn't some discovered memory leak in the C# language, it is an example of how programming mistakes in garbage collected languages can still lead to "memory leaks". To be more specific, memory that you intended to be freed and made available was not. You can argue about the semantics, but I think the intent of saying memory leak is clear here in the context of the article.