I've never heard it discussed before, but I think the "no data" part is important. Languages without pattern matching (or a few other exotic alternatives) really do not allow for proper elimination. Asynchronous message passing can be thought of as a weird continuation passing variation (you store your continuation in the message receiving code). This means all elimination is done remotely on your behalf, seemingly hiding what is a nastier part of the language.
But once you get proper elimination, now your messages can be more complex, and chained pipielines are very useful so better be synchronous if you weren't already, and then you have combinators that only shallow modify your messages so might as well immutably share memory to avoid copying, and well those objects you create and tear down on the fly might as well not be stateful because they're so short lived and woah, now we have functional programming.
But once you get proper elimination, now your messages can be more complex, and chained pipielines are very useful so better be synchronous if you weren't already, and then you have combinators that only shallow modify your messages so might as well immutably share memory to avoid copying, and well those objects you create and tear down on the fly might as well not be stateful because they're so short lived and woah, now we have functional programming.