We've added this issue to our backlog, and we will work to address it as time and resources allow. If you have any additional information or questions about this issue, please leave a comment. For additional info about issue management, please read our Triage Process.

Another workaround that I have found, in xaml give refresh view an x:Name and in code behind subscribe to the page Unloaded event and set RefreshView.Command to null

public MainPage()
{
    InitializeComponent();

    Unloaded += MainPage_Unloaded;
}

private static void MainPage_Unloaded(object? sender, EventArgs e)
{
    // Clear refresh view command to avoid memory leaks
    if (sender is MainPage mainPage && mainPage.MyRefreshView?.Command != null)
    {
        mainPage.MyRefreshView.Command = null;
    }
}

From my investigation, this will occur to any control that uses the CommandElement methods. The reason is because when the control is not used the anymore the OnCommandChanging method isn't called, neither the OnCommandChanged method, so it doesn't unsubscribre the CanExecuteChanged event, causing the control to leak.

I could find a solution for that and it's on referenced PR for this issue. But maybe the team wants to revisit how this machinery works and have some cleanup point for this kind of situation, something like DisconnectHandler.