STOMP subscription receipt can be out of order with message dispatch, resulting in consumer/client error

When a receipt[1] is specified on a subscribe frame, it is possible that a message dispatch on the newly created subscription gets delivered before the RECEIPT, causing a stomp client to error out. The perl client http://search.cpan.org/~lcons/Net-STOMP-Client-1.1/ gives

*** unexpected RECEIPT frame received: xxx 

[1] http://stomp.github.com/stomp-specification-1.1.html#Header_receipt