The situations are Resource-allocations in the parent (and caller) on behalf of the child, that the child must return to the pool on end, but wants to do in the caller because of lexical restrictions or clarity of writing.

Do you often find yourself writing subroutines that may or may not need to fork?

Of course in testing and debugging. Debugging a (multiply) forked sub is a PITA(TM).