Hi, mbc.
I have been coping with the same problem for some time, and this is the best I have been able to come up with so far:
A scenario is, strictly speaking, an instance of a use case (see the definition of scenario in Rumbaugh, et al.: The Unified Modeling Language Reference Manual, Addison-Wesley, 1999, p. 416). For those not familiar with this terminology: an instance of a use case is a particular execution of the use case, just like you and I are particular instances of the "user" class, playing a particular role in instances of a software_development_processes.
So, the way I am handling the relationship between a scenario and its respective interaction diagram (or, when appropriate, state chart diagram) is by dragging the interaction diagram from the Workspace tree into the use case diagram, as suggested by Rafael Gonzalez in his posting in the " How to link diagrams to use cases?" thread; then, I link the use case to the interaction diagram icon with an "instantiation" relationship. This is not very orthodox, and a rigoristic methdologist will very probably give me dunce's ears and send me to a corner for this, because the "diagram" symbol is not UML. But it works, and I think I can make a pretty good argument that it is logically correct.
Works great for navigation: just double-click on the interaction diagram icon, and you navigate right into the interaction (or state chart); and viceversa: drag and drop the use case diagram into the interaction diagram, and you can navigate back to the use case diagram. It also works great in the relationship matrix, where you can obtain a panoramic view of which use cases have been instantiated.
In your particular case, I don't think it would be correct to link a note element to a use case or to an interaction diagram with an instantiation association: notes are not UML classifiers (they are just a place for free text). I would suggest something like copying the text in your note into the description of a new use case, and stereotype this new use case to «scenario» (which is totally valid even if «scenario» is not listed in the stereotype drop-down list); then join it to the original use case with an instance association. The instance of the use case (the new use case) should replace the note. This would be strict UML, but you could also proceed in the unorthodox way I have suggested.
Best wishes (and let's see what the rest of our enthusiastic community of EA users has to say).
Jaime