I realized it has nothing to do with timing but rather the current session. The job name is named something like CLEANUPUPGRADE_2013_10_22_14_23_58_757 which includes a timestamp and I guess a session id (757 in this case?) so each subsequent job in a specific session is given the same name. Is that expected behavior of the job facility in OEM or is it a bug? Seems a bug to me. Thoughts?
Apparently this is a known issue. Oracle's response -
There are some limitations related to user input for job name. These limitations are being tracked by bugs and are deferred to next release.
16689459---> EMCLI UPGRADE_AGENTS FAILS BADLY IF JOBNAME WAS REUSED
16689511---> EMCLI UNEXPECTED INPUT PARSING WHEN JOBNAME HAS SPECIAL CHARACTERS
Try submitting a new job with a new job name. Job names must be unique.