I don't think starting a new long-running conversation per async invocation is a good idea (consider using event context instead).
However you can try to use sync event and a special component to handle this use case...
component A fires sync event, component B observes sync event, calls async method on component C and stores QuartzTriggerHandle (for later manipulation)
Yes, this seems to be the perfect way for this situation. Thanks for your reply.