SDK workers are not always killed when Flink pipeline finishes

Beam python workers are spun up as part of a pipeline execution, and killed once that pipeline has been cancelled or failed. However, in some situations we see the workers hanging around indefinitely until they are manually killed or the taskmanager is restarted. The behavior seems to only occur with streaming pipelines, and appears non-deterministic