`PREFECT_DEFAULT_WORK_POOL_NAME` is ignored when deploying multiple flows with `prefect deploy`

[uncycler]

Bug summary

I'm trying to deploy multiple flows with a default work pool but the pool argument is ignored:

$> prefect --no-prompt deploy --all --pool mypool

A work pool is required to deploy this flow. Please specify a work pool name via the '--pool' flag or in your prefect.yaml 
file.

The same thing happened with PREFECT_DEFAULT_WORK_POOL_NAME. It works fine when specifying the flow name or if there is only one flow defined in prefect.yaml.

Version info (prefect version output)

Version:             3.0.10
API version:         0.8.4
Python version:      3.12.7
Git commit:          3aa2d893
Built:               Tue, Oct 15, 2024 1:31 PM
OS/Arch:             linux/x86_64
Profile:             ephemeral
Server type:         server
Pydantic version:    2.9.2
Integrations:
  prefect-kubernetes: 0.5.1

Additional context

deployments:
  - name: test1
    entrypoint: gowiththeflow.py:flow1
  - name: test2
    entrypoint: gowiththeflow.py:flow2