X.25 and OSI are, of course, notable (they are also closely related; X.25 predates OSI, and OSI could be run on top of it. Both were developed by ITU-T. Both are now obsolete). GPRS, the tunneling protocol of the GSM stack, probably also deserves note (Though the role of GPRS is more analogous to PPP or L2TP than IP).
You might also consider the specialized protocols (Such as ProfiBus) that run on specialized industrial/embedded networks (Such as CAN, Controller Area Network) in this category. They certainly fall in the same place in the OSI model. The same applies to the constituent protocols of the BlueTooth stack.
The 802.15.4 standard for 'low powered wireless personal area networks' probably comes closest to the old days of 'lots of different protocols running on Ethernet', however. In common usage on top of it are the protocols ZigBee (Somewhat heavyweight device-device protocol), MiWi (A lightweight and proprietary alternative) and 6lowPAN (An encapsulation for IPv6 on top of the 802.15.4 and an adaption layer - something needed when your underlying transport has a maximum frame size lower than IPv6's minimum!
)
Finally: NetBEUI isn't a protocol. It is the name IBM assigned to an extension to a DOS API called NetBIOS when it released an early network card, to support existing apps designed for NetBIOS (introduced by a competing company). This card spoke NetBIOS Frames (NBF) on top of Ethernet. As the world moved towards unifying behind a TCP/IP transport, an RFC was standardized specifying a protocol for transporting NetBIOS data on top of IPv4; this standard is called NBT.
The only user of NetBIOS in the recent past has been Microsoft, but they have dropped support for it from Vista (and good riddance to that! NetBIOS is a mess!). For some reason they have always called NetBIOS NetBEUI in their implementation. This is how that name confusion got started.