Any reason why AuthenticationStateChanged would re-create a Blazor Wasm @page component?

[oatsoda]

Given this App.razor

<CascadingAuthenticationState>
    <Router AppAssembly="@typeof(App).Assembly">
        <Found Context="routeData">
            <AuthorizeRouteView RouteData="@routeData">
                <NotAuthorized>
                    <NotAuthorizedHandler /> @* custom component *@
                </NotAuthorized>
            </AuthorizeRouteView>
        </Found>
        <NotFound>
            <LayoutView Layout="@typeof(NotFound_Layout)">
                <NotFoundPage /> @* custom component *@
            </LayoutView>
        </NotFound>
    </Router>
</CascadingAuthenticationState>

and given a custom AuthenticationService which I can set some authentication state and raise the authentication state changed event:

public class CustomAuthService  // ... derived from RemoveAuthenticationService etc.
{
     public void SetAuthenticationState()
     {
         var principal = // set some claims principal in state somewhere         
         NotifyAuthenticationStateChanged(Task.Run(() => new AuthenticationState(principal)));
     }
}

and a basic non-authenticated (anon) page:

@page "/some-url"

@code 
{
    [Inject]
    public CustomAuthService CustomAuthService { get; set; }

    protected override async Task OnInitializedAsync()
    {
          Console.WriteLine($"Page OnInit {GetHashCode()}");
          
          // Set the auth state
          CustomAuthService.SetAuthenticationState();
    }
}

When I execute this code - which moves the authentication from Not Authenticated to Authenticated, the Page Component gets created again and the OnInit fires for a second time.

Is there a reason for this? I have been through the CascadingAuthenticationState, Router and various Blazor components but couldn't find any logic which causes the render tree to drop the first instance and create a new one.