Unexpected behaviour: destroying resource tfe_workspace_run triggers destroy run of workspace’s managed resources

[KatjaLeberwurst]

Terraform Enterprise version

v202410-1

Terraform version

Terraform Version: v1.7.4
tfe-Provider Version: 0.58.0

Terraform Configuration Files

terraform {
  required_version = ">= 0.12"

  cloud {

    hostname     = "hostname"
    organization = "organization"

    workspaces {
      name = "managment-workspace"
    }
  }
  required_providers {
    tfe = {
      version = "0.58.0"
      source = "hashicorp/tfe"
    }
  }
}

provider "tfe" {
  hostname = "hostname"
}

resource "tfe_workspace" "workspace" {
  name                  = "workspacename"
  organization          = "organization"
  speculative_enabled   = true
  file_triggers_enabled = true
  auto_apply            = true
  force_delete          = false
}

resource "tfe_workspace_settings" "workspace_settings" {
  workspace_id   = tfe_workspace.workspace.id
  execution_mode = "remote"
}

resource "tfe_workspace_run" "ws_run" {
  workspace_id = tfe_workspace.workspace.id

  destroy {
    manual_confirm = false
    retry          = false
    wait_for_run   = true
  }
}

Debug Output

...

Expected Behavior

In the past, we have included the resource tfe_workspace_run in our Terraform configuration to ensure that the corresponding workspace is only deleted when the resources managed in it have already been destroyed. This also worked. 
However, as we no longer need this tfe_workspace_run resource, we have removed it from our Terraform configuration and executed a Terraform plan. The plan indicated that only this resource would be destroyed, which is exactly what we would have expected. For this reason, we triggered Terraform Apply.

Actual Behavior

However, terraform apply resulted in all resources managed by the corresponding workspace being destroyed and then the tfe_workspace_run resource. Is the behavior a bug or was it to be expected that all resources managed by the workspace were destroyed?

Additional Context