There is no difference between a "single" and a "multiple" selector. As far as jQuery is concerned, it is a (potentially empty) group of elements.
.on and .off, for example, will apply/remove the event handler on each of the elements in the group. If that group happens to be empty, then nothing happens.
In some ways, this is a good thing - it removes the need for manually checking it. However, I tend to see it as a problem. Let's say I write:
document.getElementById('button1').addEventListener(...);
But #button1 does not exist on the page. I get an error telling me such (sort of - "Unable to get property 'addEventListener' of undefined or null reference" is not immediately obvious but you learn to understand it) and I can resolve the problem either by fixing the absence of the desired element, or adding a check to explicitly say "it's okay if there isn't such an element".
However in jQuery you don't get that choice. Typo in your selector? The empty collection is handled just fine and events mysteriously disappear. I consider this to be a bad thing personally, but there's no way for jQuery to know whether you intended for zero, one, or hundreds of elements to match...