Sorry you are right, that was specific to our case where we were already waiting for a result from the goroutines.
In an actor model, you would let the "goroutine" die and the supervisor would restart it if it has a restart policy, otherwise it will die and stay dead (without bringing the system down).
In erlang you can also "link" the current actor to another actor so that if the linked actor dies, the linker dies too (or receives a message)