A Spark application utilizes a broadcast variable to share a small configuration dataset with all executors. The application performs a heavy transformation using this variable in the initial stage, but the variable is not required for the remaining duration of the job. To prevent the broadcast variable from consuming executor memory and causing resource exhaustion in the later stages, what is the most effective method?