Ok, let's leave bindAsEventListener as it is for
now, although I remember seeing it "misused" much more
often that is is used "properly". Main reason must be the fact that
bindAsEventListener just sounds necessary to
use when binding event listeners. Without reading documentation it
might seem obvious to a beginner, that good old bind
is somehow not sufficient :)

By adding couple more lines, we would fool-proof future use and
give an immediate boost to existing code. We could still explain
the proper usage, of course.

We all know how ofter wrap/methodize
are used internally, so I think it's important that we change those
methods. bindAsEventListener and curry
need this to a lesser extent, but would bring some consistency
(with no downsides, but code size)