Someone on the flightbeam forum told me (Because I also have this issue in San Fransisco) that is has something to do with the AES.
It would have been helpful if you said you had AES installed. Yes, of course, AES can cause this, if it's not installed properly or configured in the wrong way.
Since the current version KLAS uses SODE jetways, and latest sceneries for Flightbeam use it too, you must turn off AES at such airports, otherwise it will try to add its own jetways, without being able to exclude the ones that comes with the scenery, which cannot be excluded anymore in the standard way (using AFCAD exclude areas that comes with AES), since they are not standard.