Not sure what you mean? This is exactly what I checked and confirmed it doesn't work. The module is being loaded after rebooting no matter the modprobe.d blacklisting.
This is what I did, actually, and that works, but one would expect the standard modprobe.conf/modprobe.d method work, too. Especially since it is mentioned here in the forums as a viable solution as well, so I expect this is, in fact, a bug.